Customizing Purchase Order and Invoice Line Descriptions for Microsoft Azure
Customizing the fields in Microsoft Azure purchase orders and invoice descriptions can improve their readability. It helps customers with access to the invoices to map their usage data better. We are adding this capability as well as the following enhancements for Microsoft Azure purchase orders and invoices:
- New pre-defined parameters that can be added to the description of a purchase order line
- Granular Cost Category identification for each usage line
- Additional fields to define the aggregation parameter
The following table lists all the new parameters and their availability for each cost category:
Cost Category | Description | Available Parameters |
---|---|---|
Azure-RI | Reserved Instance Usages | PREFIX PRODUCT_ID PRODUCT_NAME SKU_ID UNIT_TYPE CHARGE_START_DATE CHARGE_END_DATE SKU_NAME AZURE_PLAN_SUBSCRIPTION_ID RESERVATION_ORDER_ID TERM_AND_BILLING_CYCLE BILLING_FREQUENCY CHARGE_TYPE PUBLISHER_NAME SUBSCRIPTION_ID ALTERNATE_ID |
Azure-Third-Party-IaaS | Third Party IaaS usages | |
Azure-Third-Party-SaaS | Third Party SaaS usages | |
Azure-Credit | Customer Credits | |
Azure-IaaS-Cancel-Refund | Cancel Immediate (Azure-Credits) | |
Azure-SaaS-Cancel-Refund | Cancel Immediate (License-Based-Credits) | |
Azure-Savings-Plan | Azure Savings plan usages | |
Azure-Plan-With-PEC | Azure Plan usage with Partner Earned Credits(PEC) when Simplified Usage Processing feature is enabled. | |
Azure-Plan-Without-PEC | Azure Plan usage without PEC when Simplified Usage Processing feature is enabled. | |
Azure-Plan-With-PEC | Azure Plan usage with Partner Earned Credits(PEC) | PREFIX PRODUCT_ID PRODUCT_NAME SKU_ID UNIT_TYPE CHARGE_START_DATE CHARGE_END_DATE ENTITLEMENT_ID |
Azure-Plan-Without-PEC | Azure Plan usage without PEC | |
Azure-Savings-Plan | Azure Savings plan usages from DailyRated file |
Aggregation parameters
Parameter | Availability |
---|---|
PRODUCT_ID | Available for the usage processed through Daily Rated and One Time Invoice File |
SKU_ID | Available for the usage processed through Daily Rated and One Time Invoice File |
CHARGE_START_DATE | Available for the usage processed through Daily Rated and One Time Invoice File |
CHARGE_END_DATE | Available for the usage processed through Daily Rated and One Time Invoice File |
CHARGE_TYPE | Available for the usage processed through only One Time Invoice File |
RESERVATION_ORDER_ID | Available for the usage processed through only One Time Invoice File |
BILLING_FREQUENCY | Available for the usage processed through only One Time Invoice File |
ALTERNATE_ID | Available for the usage processed through only One Time Invoice File |
In addition to these predefined parameters, customers can also add custom text and field separators in the description.
For example, if a user defines the purchase order description setting as "AzureRI-{PRODUCT_ID}_{SKU_ID};{UNIT_TYPE}
" the description is generated as "AzureRI-DZH318Z08GZP_004;1 hour
".
Symbols like -, _, ; are used as separators and are displayed as-is in the description. Similarly, AzureRI
is the static additional text (prefix) used in the description settings.
Feature enablement
The feature is not enabled by default. Contact your AppDirect technical representative to request it.
Setting enablement
Setting enablement is required. Contact your AppDirect technical representative for more information.
Documentation
No documentation updates are required.
Was this page helpful?
Tell us more…
Help us improve our content. Responses are anonymous.
Thanks
We appreciate your feedback!